@weltenwort I pulled these instructions from a comment you made on an older issue from last year. I was hoping you could take a look and make sure this is still applicable or if there are changes that need to be made?

Hi @mdbirnstiehl, thanks for the ping. This approach makes sense for existing deployments that don't use advanced setting mentioned above for historic reasons. Any newer deployments default to using the advanced setting and a manipulation of the log view saved object might therefore not have any effect. AFAIK in serverless that saved object type doesn't exist at all.
So if we want to include this approach I feel we should add lots of caveat warnings around it. Does that help?

Thanks @weltenwort, that does make sense. There's a discussion in the issue for this PR, where I think what we actually want to document is using the Advanced Settings saved object. I'm not sure if the process to use Advanced Settings saved object would be similar to this or if the process would differ.

The process would be similar, but the downside is that one couldn't just export/import this one setting selectively. It would always apply to all settings.

For users that use configuration management for Kibana deployments, there is the option to define overrides to individual settings in the yaml file like this:

uiSettings:
  overrides:
    'observability:logSources': ["logs-somewhere-else"]

But I'm not sure if that is an officially supported setting or not 🤔